Skip to content

Conversation

@Avish34
Copy link
Contributor

@Avish34 Avish34 commented Sep 15, 2025

Package identifier and version are required for some of the registries else we won't be able to pull the meta data to validate the packages.

Motivation and Context

This is in continuation to #424

How Has This Been Tested?

Unit test.

Breaking Changes

No

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

@Avish34
Copy link
Contributor Author

Avish34 commented Sep 15, 2025

@domdomegg please review!

domdomegg
domdomegg previously approved these changes Sep 20, 2025
Copy link
Member

@domdomegg domdomegg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Avish34 Avish34 force-pushed the extra-validations branch 4 times, most recently from ca3a896 to 0bd9bae Compare September 22, 2025 17:10
@domdomegg domdomegg merged commit 31e16a1 into modelcontextprotocol:main Sep 23, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants